Plugging your PS5 controller into your PC with a USB cable doesn’t always mean you get the fastest response. For one specific controller, that cable can actually make things a bit slower than staying on Bluetooth.
That’s because speed comes from how often the controller is allowed to report its position, and the firmware sets a different rate for each connection mode. Your DualSense uses a low default report rate over USB on PC while Bluetooth can reach higher, so the same controller on the same PC measures differently depending on how you connect it. On Reddit, owners who expected wired to win found Bluetooth reporting faster in their own tests. Once you know how to read your controller’s actual report rate in DS4Windows and how to run a 30-second check on TestMyGamepad, you can see in seconds which mode is actually faster on your setup — here’s the check that changes the decision.
Why wired is not automatically faster for DualSense on PC
Input lag for a DualSense on PC comes from the report rate the firmware uses for each mode, not from whether a cable is present. The controller has to wait for its turn to send an update, and that turn is scheduled by its USB descriptor on the wired side and by its radio negotiation on the Bluetooth side.
Stock DualSense ships with a USB descriptor interval that limits wired reports. The project notes that configured DualSense default USB interval is 6, which translates to an actual interval of about 4ms or 250Hz over USB on PC. The same controller over Bluetooth can negotiate a 1ms interval, about 1000Hz, on a capable adapter, which is why a wireless link can deliver more frequent reports than the cable you just plugged in.
That difference is visible in community measurements. DS4Windows latency docs document DualSense Bluetooth around 1ms versus wired around 3ms in their guide, and note that changing the polling setting alters the interval. Wired still goes through the Windows USB HID stack, Bluetooth goes through the Windows Bluetooth stack with its own overhead, but the firmware’s capped wired rate is the reason the cable doesn’t win by default.
Sony controls both ends on PS5, so the console can tune the link. On PC you use a generic Bluetooth stack, which means adapter quality, driver version, and interference matter. The Bluetooth SIG Core 5.1 page explains the qualified data rate features the radio can use, not the game-specific latency you will feel, so a Bluetooth Qualification does not promise a lower input lag figure — it only defines what the radio is qualified to do.
Diagram showing DualSense to PC via USB path labeled about 4ms default interval and via Bluetooth path labeled about 1ms interval, with note that firmware sets rate per mode.
Before committing, check DS4Windows settings panel for polling rate reading — connect the same controller wired then Bluetooth on the same PC and note the reported interval.
What polling rate your DualSense actually uses in each mode
Whether Bluetooth or wired is better for a PS5 controller on PC comes down to what rate the controller actually uses in each mode on your PC.
On a stock Windows 11 PC, DualSense CFI-ZCT1W typically polls about 250Hz wired. Community logs show 3 to 3.5ms readings with a USB descriptor interval of 6, which the DualSense overclock intervals documentation describes as the default over USB. The same tooling notes that interval 4 corresponds to 1ms or 1000Hz, and interval 1 corresponds to 0.125ms or 8000Hz when overclocked, so the hardware can go higher once the descriptor is overridden.
Over Bluetooth, that same DualSense often reaches about 1000Hz on a decent external adapter. The polling rate test tool notes DualSense can poll at 1000Hz via Bluetooth compared to 250Hz via USB-C natively on PC, when you move sticks in a circle for 30 seconds. DualSense Edge is different — it can hold 1000Hz over both wired and Bluetooth in many setups.
Measured input latency follows the same inversion. The ResetEra latency comparison list records DualSense Bluetooth at about 4.9ms and DualSense wired at about 11.1ms stock, with DualSense wired overclocked to 1k dropping to about 3.7ms and to 8k dropping to about 1.8ms, while DualShock 4 wired sits around 13.6ms. That shows why the faster-sounding cable measures slower before overclocking.
Xbox controllers behave the opposite. A Microsoft Q&A answer notes the Xbox polling rate case where an Xbox Series controller tested about 60Hz polling and about 15ms latency via Wireless Adapter versus about 7ms latency and 125Hz wired. Findings here are limited to the specific controller model tested — you can’t assume DualSense numbers carry to Xbox or third-party pads without a separate check.
How to test the latency you actually get over wired vs Bluetooth on same PC
You can run the same reproducible test on your own PC and compare wired versus Bluetooth for the exact DualSense you own.
Use the same PC, same controller, same USB port, and same Bluetooth adapter for both runs. Close heavy background apps and keep the Bluetooth dongle on an external antenna with line-of-sight, not buried behind a metal case.
Step 1: Set up DS4Windows and a browser tester
Install DS4Windows, enable its polling readout, and open gamepad polling test in a single browser tab. That site calculates average report rate in real time while you move sticks in a circle, which gives you a direct Hz reading per mode.
Step 2: Test wired first, 30 seconds moving
Connect DualSense via USB-C to a motherboard USB-A port, not a hub. Move both sticks continuously in slow circles for 30 seconds and note the average Hz and the DS4Windows interval. Stock wired often shows around 250Hz with a 3ms reading.
Step 3: Test Bluetooth on same adapter
Unplug, pair to the same Bluetooth 5.0+ adapter, and repeat the 30-second circle. Note average Hz and DS4Windows reading — Bluetooth often shows 650 to 1000Hz and about 1ms in DS4Windows input lag guide when the adapter is good. The latency test ranges page notes PS5 DualSense wired USB-C can show 4-10ms while Bluetooth can vary 15-40ms on non-PlayStation systems, because Bluetooth stack differences matter.
Step 4: Optional overclock check, same port filtering
If you use hidusbf, hidlens, or ds_oc-dkms to override bInterval, you must use the same USB port each time because the filter attaches per port. After setting interval 4 for 1000Hz, repeat the wired test and watch DS4Windows drop toward 1ms. This does not change Bluetooth — it only overrides the USB descriptor.
Table showing expected polling for DualSense wired stock versus Bluetooth and overclocked wired, with interpretation notes for DS4Windows readout.
Try this before you buy: open TestMyGamepad.com, connect DualSense wired, move sticks continuously for 30 seconds and note the Hz, then repeat on Bluetooth using the same adapter and compare the two numbers side by side.
Why assuming wired always beats Bluetooth breaks down for this model
The mistake is assuming cable equals faster because general advice says wired always wins. For DualSense on PC, Sony’s stock firmware intentionally limits wired USB polling to 250Hz while Bluetooth can reach higher, and DualShock 4 had the same history.
In a ResetEra Controllers OT thread, a poster noted DualSense Bluetooth measured 5.54ms while Xbox One wired measured 5.71ms, so wired was not universally faster and depended on controller per-mode polling. As one poster in ResetEra Controllers OT described it, “wired > 2.4GHz > Bluetooth depends on the controller”. In that thread, the solution that came up repeatedly was to use a site like Gamepadla to compare input latency per mode for the specific controller rather than assuming wired wins.
The mechanism source resolves it. The DualSense default USB polling 250Hz due to descriptor documentation explains why the same controller polls slower wired than Bluetooth on PC — the USB descriptor interval sets the wired ceiling, while Bluetooth report rate is negotiated separately. If wired shows higher stable latency than Bluetooth after your test, that’s the device’s power and USB full-speed defaults limiting sustained report rate once configured, not a broken cable.
Does Xbox and other controllers follow the same rule?
No, each brand sets its own per-mode rate, so you can’t copy DualSense numbers to an Xbox or 8BitDo pad.
Xbox Series controllers on PC show the opposite pattern. The Xbox adapter polling discussion notes 60Hz via official Wireless Adapter and 125Hz wired, measured around 15ms versus 7ms, so wired wins there. Xbox over Bluetooth varies more with Windows stack and can add jitter compared to the adapter.
Other pads split further. SCUF’s own polling-rate guidance explains SCUF Valor Pro 1K Hz polling is available on PC only in wired mode — wireless and Xbox console do not achieve 1K. 8BitDo Ultimate Bluetooth often shows 125Hz wired, Google Stadia controller 125Hz, and Xbox Elite Series 2 around 125Hz wired and 63Hz over 2.4GHz with about 8.7ms joystick latency per independent controller-latency roundups.
That comparison shows pros and cons per option, not just the recommended pick. DualSense Bluetooth gives you higher report rate out of the box without tools, but can drop or vary with interference, and you lose adaptive triggers on PC unless you use Steam Input wired. DualSense wired stock is more stable but slower at 250Hz unless you overclock, which adds CPU interrupts and requires the same USB port each time. Xbox wired is simple and stable at 125Hz, but its wireless adapter caps at 60Hz and measures higher latency. A budget 2.4GHz dongle that only does 60Hz is a genuine reason not to buy it if you play fast shooters.
Bluetooth Qualification also matters only where the claim is about the radio’s qualified data rate rather than game latency. If you need haptics and triggers on PC, Steam Input wired is the only mode that reliably passes those features through. For related guidance on headline versus delivered specs, see our guide to verify gaming gear specs for a broader rubric — this controller test is one model-specific example of that gap.
Table comparing three controllers — DualSense, Xbox Series, DualShock 4 — with columns for wired polling, Bluetooth polling, and measured latency, highlighting where Bluetooth is faster.
This comparison is research-based analysis built from publicly available specifications and community measurement databases, not a single lab test by this site. Use it as a quick-check, not a brand-wide guarantee.
How to choose the right connection for your PC setup
The right connection depends on your controller model, your adapter quality, interference in your room, and whether you need advanced features.
For DualSense on PC, Bluetooth can measure faster out of the box but is less consistent. If you have a Bluetooth 5.0+ adapter with an external antenna, low interference, and line-of-sight, Bluetooth around 1000Hz in DS4Windows often beats stock wired 250Hz in raw report rate. The trade-off is stability — Bluetooth varies with Windows stack and nearby 2.4GHz devices, and Bluetooth variability notes 15-40ms swings on non-PlayStation systems. Wired is more stable even if slower by default.
If stability matters for tournaments or you play in a crowded RF room, stay wired and consider overclocking. Overclocking via hidusbf to interval 4 for 1000Hz drops DualSense wired from about 11.1ms to about 3.7ms, and interval 1 for 8000Hz to about 1.8ms per ResetEra logs, but you must use the same USB port filtering and accept more CPU interrupts. If you need adaptive triggers and haptics on PC, you must use wired via Steam Input — Bluetooth loses those features on PC.
For Xbox controllers, the decision flips. The official Wireless Adapter measures 60Hz and about 15ms, while wired measures 125Hz and about 7ms, so wired or a good wired connection is preferred for latency. For third-party pads, check their documented polling — SCUF Valor Pro 1K is PC wired only, so wireless won’t give you 1K there.
Decision flow starting with controller model, then Bluetooth adapter quality and interference, branching to recommend wired, Bluetooth, or overclocked wired with expected polling and stability trade-off.
At your desk, check controller signal path by toggling DS4Windows polling readout while moving sticks, observing whether wired stays stable around 250Hz versus Bluetooth jumping 650-1000Hz, then pick the stable mode for your games.
The practical verdict
Stock DualSense on PC measures faster over Bluetooth than over its default USB wired mode — about 4.9ms versus about 11.1ms in community comparisons — because the firmware limits wired to about 250Hz while Bluetooth can reach about 1000Hz.
Check your actual numbers before you decide: run the 30-second TestMyGamepad circle test and DS4Windows readout for wired then Bluetooth on the same adapter.
If Bluetooth holds near 1000Hz with low jitter, use it for competitive play; if it varies or you need adaptive triggers, stay wired and consider a 1000Hz overclock on the same USB port for stability.
Frequently asked questions
Is Bluetooth really slower than wired for DualSense on PC?
No, stock DualSense polls about 250Hz wired with bInterval 6 versus up to about 1000Hz Bluetooth on a good adapter. ResetEra tests show about 4.9ms Bluetooth versus about 11.1ms wired, but Bluetooth varies with stack and interference. Wired is more stable and can be overclocked to 1000Hz.
How do I check my PS5 controller polling rate on PC?
Use TestMyGamepad and move sticks in a circle for 30 seconds for average Hz, and check DS4Windows readout showing about 3ms wired versus about 1ms Bluetooth for DualSense. Use same USB port for hidusbf filtering, and a Bluetooth 5.0+ adapter with external antenna for reliable Bluetooth reading.
Is a wired controller always faster than wireless on PC?
No, it depends on firmware report rate per mode not the cable. DualSense Bluetooth can be faster than wired stock, while Xbox Series is opposite at about 125Hz wired 7ms versus Wireless Adapter 60Hz 15ms. As ResetEra discussion noted, “wired > 2.4GHz > Bluetooth depends on the controller” so verify per model via Gamepadla.
Should I overclock my DualSense to 1000Hz wired for competitive play?
Overclocking via ds_oc tools can change bInterval from 6 to 4 for 1000Hz or 1 for 8000Hz, dropping latency from about 11.1ms to about 3.7ms at 1k and 1.8ms at 8k in ResetEra logs. It needs same USB port each time, may raise CPU interrupts, and findings apply only to tested model — stability check needed before tournament use.
